Method and apparatus for managing processing thread migration between clusters within a processor

ABSTRACT

A method, and corresponding apparatus, of managing processing thread migrations within a plurality of memory clusters, includes embedding, in memory components of the plurality of memory clusters, instructions indicative of processing thread migrations; storing, in one or more memory components of a particular memory cluster among the plurality of memory clusters, data configured to designate the particular memory cluster as a sink memory cluster, the sink memory cluster preventing an incoming migrated processing thread from migrating out of the sink memory cluster; and processing one or more processing threads, in one or more of the plurality of memory clusters, in accordance with at least one of the embedded migration instructions and the data stored in the one or more memory components of the sink memory cluster.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 13/565,749, filed Aug. 2, 2012, now U.S. Pat. No. 8,954,700, which claims the benefit of U.S. Provisional Application No. 61/514,344, filed on Aug. 2, 2011; U.S. Provisional Application No. 61/514,382, filed on Aug. 2, 2011; U.S. Provisional Application No. 61/514,379, filed on Aug. 2, 2011; U.S. Provisional Application No. 61/514,400, filed on Aug. 2, 2011; U.S. Provisional Application No. 61/514,406, filed on Aug. 2, 2011; U.S. Provisional Application No. 61/514,407, filed on Aug. 2, 2011; U.S. Provisional Application No. 61/514,438, filed on Aug. 2, 2011; U.S. Provisional Application No. 61/514,447, filed on Aug. 2, 2011; U.S. Provisional Application No. 61/514,450, filed on Aug. 2, 2011; U.S. Provisional Application No. 61/514,459, filed on Aug. 2, 2011; and U.S. Provisional Application No. 61/514,463, filed on Aug. 2, 2011. The entire teachings of the above applications are incorporated herein by reference.

BACKGROUND

The Open Systems Interconnection (OSI) Reference Model defines seven network protocol layers (L1-L7) used to communicate over a transmission medium. The upper layers (L4-L7) represent end-to-end communications and the lower layers (L1-L3) represent local communications.

Networking application aware systems need to process, filter and switch a range of L3 to L7 network protocol layers, for example, L7 network protocol layers such as, HyperText Transfer Protocol (HTTP) and Simple Mail Transfer Protocol (SMTP), and L4 network protocol layers such as Transmission Control Protocol (TCP). In addition to processing the network protocol layers, the networking application aware systems need to simultaneously secure these protocols with access and content based security through L4-L7 network protocol layers including Firewall, Virtual Private Network (VPN), Secure Sockets Layer (SSL), Intrusion Detection System (IDS), Internet Protocol Security (IPSec), Anti-Virus (AV) and Anti-Spam functionality at wire-speed.

Improving the efficiency and security of network operation in today's Internet world remains an ultimate goal for Internet users. Access control, traffic engineering, intrusion detection, and many other network services require the discrimination of packets based on multiple fields of packet headers, which is called packet classification.

Internet routers classify packets to implement a number of advanced internet services such as routing, rate limiting, access control in firewalls, virtual bandwidth allocation, policy-based routing, service differentiation, load balancing, traffic shaping, and traffic billing. These services require the router to classify incoming packets into different flows and then to perform appropriate actions depending on this classification.

A classifier, using a set of filters or rules, specifies the flows, or classes. For example, each rule in a firewall might specify a set of source and destination addresses and associate a corresponding deny or permit action with it. Alternatively, the rules might be based on several fields of a packet header including layers 2, 3, 4, and 5 of the OSI model, which contain addressing and protocol information.

On some types of proprietary hardware, an Access Control List (ACL) refers to rules that are applied to port numbers or network daemon names that are available on a host or layer 3 device, each with a list of hosts and/or networks permitted to use a service. Both individual servers as well as routers can have network ACLs. ACLs can be configured to control both inbound and outbound traffic.

SUMMARY

According to an example embodiment, a method of managing processing thread migrations within a plurality of memory clusters, includes embedding, in memory components of the plurality of memory clusters, instructions indicative of processing thread migrations; storing, in one or more memory components of a particular memory cluster among the plurality of memory clusters, data configured to designate the particular memory cluster as a sink memory cluster, the sink memory cluster preventing an incoming migrated processing thread from migrating out of the sink memory cluster; and processing one or more processing threads, in one or more of the plurality of memory clusters, in accordance with at least one of the embedded migration instructions and the data stored in the one or more memory components of the sink memory cluster.

According to another example embodiment, an apparatus of managing processing thread migrations within a plurality of memory clusters, includes one or more processors configured to cause embedding, in memory components of the plurality of memory clusters, of instructions indicative of processing thread migrations; cause storing, in one or more memory components of a particular memory cluster among the plurality of memory clusters, of data configured to designate the particular memory cluster as a sink memory cluster, the sink memory cluster preventing an incoming migrated processing thread from migrating out of the sink cluster; and process one or more processing threads, in one or more of the plurality of memory clusters, in accordance with at least one of the embedded migration instructions and the data stored in the one or more memory components of the sink memory cluster.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing will be apparent from the following more particular description of example embodiments of the invention, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating embodiments of the present invention.

FIG. 1 is a block diagram of a typical network topology including network elements where a search processor may be employed.

FIGS. 2A-2C show block diagrams illustrating example embodiments of routers employing a search processor.

FIG. 3 shows an example architecture of a search processor.

FIG. 4 is a block diagram illustrating an example embodiment of loading rules, by a software compiler, into an on-chip memory (OCM).

FIG. 5 shows a block diagram illustrating an example embodiment of a memory, or search, cluster.

FIGS. 6A-6B show block diagrams illustrating example embodiments of transport operations between two search clusters.

FIG. 7 shows an example hardware implementation of the OCM in a search cluster.

FIGS. 8A to 8E show block and logic diagrams illustrating an example implementation of a crossbar controller (XBC).

FIGS. 9A to 9D show block and logic diagrams illustrating an example implementation of a crossbar (XBAR) and components therein.

FIGS. 10A and 10B show two example tables storing resource state information in terms of credits.

FIGS. 11A to 11C illustrate examples of interleaving transport operations and partial transport operations over consecutive clock cycles.

FIGS. 12A and 12B show flowcharts illustrating methods of managing transport operations between a first memory cluster and one or more other memory clusters performed by the XBC.

FIG. 13 shows a flowchart illustrating a method of assigning resources used in managing transport operations between a first memory cluster and one or more other memory clusters.

FIG. 14 shows a flow diagram illustrating a deadlock scenario in processing thread migrations between two memory clusters.

FIG. 15 shows a graphical illustration of an approach to avoid deadlock in processing thread migrations.

FIG. 16 is a flowchart illustrating a method of managing processing thread migrations within a plurality of memory clusters.

DETAILED DESCRIPTION

A description of example embodiments of the invention follows.

Although packet classification has been widely studied for a long time, researchers are still motivated to seek novel and efficient packet classification solutions due to: i) the continued growth of network bandwidth, ii) increasing complexity of network applications, and iii) technology innovations of network systems.

Explosion in demand for network bandwidth is generally due to the growth in data traffic. Leading service providers report bandwidths doubling on their backbone networks about every six to nine months. As a consequence, novel packet classification solutions are required to handle the exponentially increasing traffics on both edge and core devices.

Complexity of network applications is increasing due to the increasing number of network applications being implemented in network devices. Packet classification is widely used for various kinds of applications, such as service-aware routing, intrusion prevention and traffic shaping. Therefore, novel solutions of packet classification must be intelligent to handle diverse types of rule sets without significant loss of performance.

In addition, new technologies, such as multi-core processors provide unprecedented computing power, as well as highly integrated resources. Thus, novel packet classification solutions must be well suited to advanced hardware and software technologies.

Existing packet classification algorithms trade memory for time. Although the tradeoffs have been constantly improving, the time taken for a reasonable amount of memory is still generally poor.

Because of problems with existing algorithmic schemes, designers use ternary content-addressable memory (TCAM), which uses brute-force parallel hardware to simultaneously check packets against all rules. The main advantages of TCAMs over algorithmic solutions are speed and determinism. TCAMs work for all databases.

A TCAM is a hardware device that functions as a fully associative memory. A TCAM cell stores three values: 0, 1, or ‘X,’ which represents a don't-care bit and operates as a per-cell mask enabling the TCAM to match rules containing wildcards, such as a kleene star ‘*’. In operation, a whole packet header can be presented to a TCAM to determine which entry, or rule, it matches. However, the complexity of TCAMs has allowed only small, inflexible, and relatively slow implementations that consume a lot of power. Therefore, a need continues for efficient algorithmic solutions operating on specialized data structures.

Current algorithmic methods remain in the stages of mathematical analysis and/or software simulation, that is observation based solutions.

Proposed mathematic solutions have been reported to have excellent time/spatial complexity. However, methods of this kind have not been found to have any implementation in real-life network devices because mathematical solutions often add special conditions to simplify a problem and/or omit large constant factors which might conceal an explicit worst-case bound.

Proposed observation based solutions employ statistical characteristics observed in rules to achieve efficient solution for real-life applications. However, these algorithmic methods generally only work well with a specific type of rule sets. Because packet classification rules for different applications have diverse features, few observation based methods are able to fully exploit redundancy in different types of rule sets to obtain stable performance under various conditions.

Packet classification is performed using a packet classifier, also called a policy database, flow classifier, or simply a classifier. A classifier is a collection of rules or policies. Packets received are matched with rules, which determine actions to take with a matched packet. Generic packet classification requires a router to classify a packet on the basis of multiple fields in a header of the packet. Each rule of the classifier specifies a class that a packet may belong to according to criteria on ‘F’ fields of the packet header and associates an identifier, e.g., class ID, with each class. For example, each rule in a flow classifier is a flow specification, in which each flow is in a separate class. The identifier uniquely specifies an action associated with each rule. Each rule has ‘F’ fields. An ith field of a rule R, referred to as R[i], is a regular expression on the ith field of the packet header. A packet P matches a particular rule R if for every i, the ith field of the header of P satisfies the regular expression R[i].

Classes specified by the rules may overlap. For instance, one packet may match several rules. In this case, when several rules overlap, an order in which the rules appear in the classifier determines the rules relative priority. In other words, a packet that matched multiple rules belongs to the class identified by the identifier, class ID, of the rule among them that appears first in the classifier.

Packet classifiers may analyze and categorize rules in a classifier table and create a decision tree that is used to match received packets with rules from the classifier table. A decision tree is a decision support tool that uses a tree-like graph or model of decisions and their possible consequences, including chance event outcomes, resource costs, and utility. Decision trees are commonly used in operations research, specifically in decision analysis, to help identify a strategy most likely to reach a goal. Another use of decision trees is as a descriptive means for calculating conditional probabilities. Decision trees may be used to match a received packet with a rule in a classifier table to determine how to process the received packet.

In simple terms, the problem may be defined as finding one or more rules, e.g., matching rules, that match a packet. Before describing a solution to this problem, it should be noted that a packet may be broken down into parts, such as a header, payload, and trailer. The header of the packet, or packet header, may be further broken down into fields, for example. So, the problem may be further defined as finding one or more rules that match one or more parts of the packet.

A possible solution to the foregoing problem(s) may be described, conceptually, by describing how a request to find one or more rules matching a packet or parts of the packet, a “lookup request,” leads to finding one or more matching rules.

FIG. 1 is a block diagram 100 of a typical network topology including network elements where a search processor may be employed. The network topology includes an Internet core 102 including a plurality of core routers 104 a-h. Each of the plurality of core routers 104 a-h is connected to at least one other of the plurality of core routers 104 a-h. Core routers 104 a-h that are on the edge of the Internet core 102, e.g., core routers 104 b-e and 104 h, are coupled with at least one edge router 106 a-f. Each edge router 106 a-f is coupled to at least one access router 108 a-e.

The core routers 104 a-104 h are configured to operate in the Internet core 102 or Internet backbone. The core routers 104 a-104 h are configured to support multiple telecommunications interfaces of the Internet core 102 and are further configured to forward packets at a full speed of each of the multiple telecommunications protocols.

The edge routers 106 a-106 f are placed at the edge of the Internet core 102. Edge routers 106 a-106 f bridge access routers 108 a-108 e outside the Internet core 102 and core routers 104 a-104 h in the Internet core 102. Edge routers 106 a-106 f may be configured to employ a bridging protocol to forward packets from access routers 108 a-108 e to core routers 104 a-104 h and vice versa.

The access routers 108 a-108 e may be routers used by an end user, such as a home user or an office, to connect to one of the edge routers 106 a-106 f, which in turn connects to the Internet core 102 by connecting to one of the core routers 104 a-104 h. In this manner, the edge routers 106 a-106 f may connect to any other edge router 106 a-106 f via the edge routers 106 a-106 f and the interconnected core routers 104 a-104 h.

The search processor described herein may reside in any of the core routers 104 a-104 h, edge routers 106 a-106 f, or access routers 108 a-108 e. The search processor described herein, within each of these routers, is configured to analyze Internet protocol (IP) packets based on a set of rules and forward the IP packets along an appropriate network path.

FIG. 2A is a block diagram 200 illustrating an example embodiment of an edge router 106 employing a search processor 202. An edge router 106, such as a service provider edge router, includes the search processor 202, a first host processor 204 and a second host processor 214. Examples of the first host processor include processors such as a network processor unit (NPU), a custom application-specific integrated circuit (ASIC), an OCTEON® processor available from Cavium Inc., or the like. The first host processor 204 is configured as an ingress host processor. The first host processor 204 receives ingress packets 206 from a network. Upon receiving a packet, the first host processor 204 forwards a lookup request including a packet header, or field, from the ingress packets 206 to the search processor 202 using an Interlaken interface 208. The search processor 202 then processes the packet header using a plurality of rule processing engines employing a plurality of rules to determine a path to forward the ingress packets 206 on the network. The search processor 202, after processing the lookup request with the packet header, forwards the path information to the first host processor 204, which forwards the processed ingress packets 210 to another network element in the network.

Likewise, the second host processor 214 is an egress host processor. Examples of the second host processor include processors such as a NPU, a custom ASIC, an OCTEON processor, or the like. The second host processor 214 receives egress packets 216 to send to the network. The second host processor 214 forwards a lookup request with a packet header, or field, from the egress packets 216 to the search processor 202 over a second Interlaken interface 218. The search processor 202 then processes the packet header using a plurality of rule processing engines employing a plurality of rules to determine a path to forward the packets on the network. The search processor 202 forwards the processed egress packets 220 from the host processor 214 to another network element in the network.

FIG. 2B is a block diagram 220 illustrating another example embodiment of an edge router 106 configured to employ the search processor 202. In this embodiment, the edge router 106 includes a plurality of search processors 202, for example, a first search processor 202 a and a second search processor 202 b. The plurality of search processors 202 a-202 b are coupled to a packet processor 228 using a plurality of Interlaken interfaces 226 a-b, respectively. Examples of the packet processor 228 include processors such as NPU, ASIC, or the like. The plurality of search processors 202 a-202 b may be coupled to the packet processor 228 over a single Interlaken interface. The edge router 106 receives a lookup request with a packet header, or fields, of pre-processed packets 222 at the packet processor 228. The packet processor 228 sends the lookup request to one of the search processors 202 a-202 b. The search processor, 202 a or 202 b, searches a packet header for an appropriate forwarding destination for the pre-processed packets 222 based on a set of rules and data within the packet header, and responds to the lookup request to the packet processor 228. The packet processor 228 then sends the post processed packets 224 to the network based on the response to the lookup request from the search processors 202 a-202 b.

FIG. 2C is a block diagram 240 illustrating an example embodiment of an access router 246 employing the search processor 202. The access router 246 receives an input packet 250 at an ingress packet processor 242. Examples of the ingress packet processor 242 include OCTEON processor, or the like. The ingress packet processor 242 then forwards a lookup request with a packet header of the input packet 250 to the search processor 202. The search processor 202 determines, based on packet header of the lookup request, a forwarding path for the input packet 250 and responds to the lookup requests over the Interlaken interface 252 to the egress packet processor 244. The egress packet processor 244 then outputs the forwarded packet 248 to the network.

FIG. 3 shows an example architecture of a search processor 202. The processor includes, among other things, an interface, e.g., Interlaken LA interface, 302 to receive requests from a host processor, e.g., 204, 214, 228, 242, or 244, and to send responses to the host processor. The interface 302 is coupled to Lookup Front-end (LUF) processors 304 configured to process, schedule, and order the requests and responses communicated from or to the interface 302. According to an example embodiment, each of the LUF processors is coupled to one of the super clusters 310. Each super cluster 310 includes one or more memory clusters, or search clusters, 320. Each of the memory, or search, clusters 320 includes a Lookup Engine (LUE) component 322 and a corresponding on-chip memory (OCM) component 324. A memory, or search, cluster may be viewed as a search block including a LUE component 322 and a corresponding OCM component 324. Each LUE component 322 is associated with a corresponding OCM component 324. A LUE component 322 includes processing engines configured to search for rules in a corresponding OCM component 324, given a request, that match keys for packet classification. The LUE component 322 may also include interface logic, or engine(s), configured to manage transport of data between different components within the memory cluster 320 and communications with other clusters. The memory clusters 320, in a given super cluster 310, are coupled through an interface device, e.g., crossbar (XBAR) 312. The XBAR 312 may be viewed as an intelligent fabric enabling coupling LUF processors 304 to different memory clusters 320 as well as coupling between different memory clusters 320 in the same super cluster 310. The search processor 202 may include one or more super clusters 310. A lookup cluster complex (LCC) 330 defines the group of super clusters 310 in the search processor 202.

The search processor 202 may also include a memory walker aggregator (MWA) 303 and at least one memory block controller (MBC) 305 to coordinate read and write operations from/to memory located external to the processor. The search processor 202 may further include one or more Bucket Post Processors (BPPs) 307 to search rules, which are stored in memory located external to the search processor 202, that match keys for packet classification.

FIG. 4 is a block diagram 400 illustrating an example embodiment of loading rules, by a software compiler, into OCM components. According to an example embodiment, the software compiler 404 is software executed by a host processor or control plane processor to store rules into the search processor 202. Specifically, rules are loaded to at least one OCM component 324 of at least one memory cluster, or search block, 320 in the search processor 202. According to at least one example embodiment, the software compiler 404 uses multiple data structures, in storing the rules, in a way to facilitate the search of the stored rules at a later time. The software compiler 404 receives a rule set 402, parameter(s) indicative of a maximum tree depth 406 and parameter(s) indicative of a number of sub-trees 408. The software compiler 404 generates a set of compiled rules formatted, according at least one example embodiment, as linked data structures referred to hereinafter as rule compiled data structure (RCDS) 410. The RCDS is stored in at least one OCM component 324 of at least one memory cluster, or search block, 320 in the search processor 202. The RCDS 410 includes at least one tree 412. Each tree 412 includes nodes 411 a-411 c, leaf nodes 413 a-413 b, and a root node 432. A leaf node, 413 a-413 b, of the tree 412 includes or points to one of a set of buckets 414. A bucket 414 may be viewed as a sequence of bucket entries, each bucket entry storing a pointer or an address, referred to hereinafter as a chunk pointer 418, of a chunk of rules 420. Buckets may be implemented, for example, using tables, linked lists, or any other data structures known in the art adequate for storing a sequence of entries. A chunk of rules 420 is basically a chunk of data describing or representing one or more rules. In other words, a set of rules 416 stored in one or more OCM components 324 of the search processor 202 include chunks of rules 420. A chunk of rules 420 may be a sequential group of rules, or a group of rules scattered throughout the memory, either organized by a plurality of pointers or by recollecting the scattered chunk of rules 420, for example, using a hash function.

The RCDS 410 described in FIG. 4 illustrates an example approach of storing rules in the search processor 202. A person skilled in the art should appreciate that other approaches of using nested data structures may be employed. For example, a table with entries including chunk pointers 418 may be used instead of the tree 412. In designing a rule compiled data structure for storing and accessing rules used to classify data packets, one of the factors to be considered is enabling efficient and fast search or access of such rules.

Once the rules are stored in the search processor 202, the rules may then be accessed to classify data packets. When a host processor receives a data packet, the host processor forwards a lookup request with a packet header, or field, from the data packet to the search processor 202. On the search processor side, a process of handling the received lookup request includes:

1) The search processor receives the lookup request from the host processor. According to at least one example embodiment, the lookup request received from the host processor includes a packet header and a group identifier (GID).

2) The GID indexes an entry in a global definition/description table (GDT). Each GDT entry includes n number of table identifiers (TID), a packet header index (PHIDX), and key format table index (KFTIDX).

3) Each TID indexes an entry in a tree location table (TLT). Each TLT entry identifies which lookup engine or processor will look for the one or more matching rules. In this way, each TID specifies both who will look for the one or more matching rules and where to look for the one or more matching rules.

4) Each TID also indexes an entry in a tree access table (TAT). TAT is used in the context in which multiple lookup engines, grouped together in a super cluster, look for the one or more matching rules. Each TAT entry provides the starting address in memory of a collection of rules, or pointers to rules, called a table or tree of rules. The terms table of rules or tree of rules, or simply table or tree, are used interchangeably hereinafter. The TID identifies which collection or set of rules in which to look for one or more matching rules.

5) The PHIDX indexes an entry in a packet header table (PHT). Each entry in the PHT describes how to extract n number of keys from the packet header.

6) The KFTIDX indexes an entry in a key format table (KFT). Each entry in the KFT provides instructions for extracting one or more fields, e.g., parts of the packet header, from each of the n number of keys, which were extracted from the packet header.

7) Each of the extracted fields, together with each of the TIDs are used to look for subsets of the rules. Each subset contains rules that may possibly match each of the extracted fields.

8) Each rule of each subset is then compared against an extracted field. Rules that match are provided in responses, or lookup responses.

The handling of the lookup request and its enumerated stages, described above, are being provided for illustration purposes. A person skilled in the art should appreciate that different names as well as different formatting for the data included in a look up request may be employed. A person skilled in the art should also appreciate that at least part of the data included in the look up request is dependent on the design of the RCDS used in storing matching rules in a memory, or search, cluster 320.

FIG. 5 shows a block diagram illustrating an example embodiment of a memory, or search, cluster 320. The memory, or search, cluster 320 includes an on-chip memory (OCM) 324, a plurality of processing, or search, engines 510, an OCM bank slotter (OBS) module 520, and a cross-bar controller (XBC) 530. The OCM 324 includes one or more memory banks. According to an example implementation, the OCM 324 includes two megabytes (MBs) of memory divided into 16 memory banks. According to the example implementation, the OCM 324 includes 64 k, or 65536, of rows each 256 bits wide. As such, each of the 16 memory banks has 4096 contiguous rows, each 256 bits wide. A person skilled in the art should appreciate that the described example implementation is provided for illustration and the OCM may, for example, have more or less than 2 MBs of memory and the number of memory banks may be different from 16. The number of memory rows, the number of bits in each memory row, as well as the distribution of memory rows between different memory banks may be different from the illustration in the described example implementation. The OCM 324 is configured to store, and provide access to, the RCDS 410. In storing the RCDS 410, the distribution of the data associated with the RCDS 410 among different memory banks may be done in different ways. For example, different data structures, e.g., the tree data structure(s), the bucket storage data structure(s), and the chunk rule data structure(s), may be stored in different memory banks. Alternatively, a single memory bank may store data associated with more than one data structure. For example, a given memory bank may store a portion of the tree data structure, a portion of the bucket data structure, and a portion of the chunk rule data structure.

The plurality of processing engines 510 include, for example, a tree walk engine (TWE) 512, a bucket walk engine (BWE) 514, one or more rule walk engines (RWE) 516, and one or more rule matching engines (RME) 518. When the search processor 202 receives a request, called a lookup request, from the host processor, the LUF processor 304 processes the lookup request into one or more key requests, each of which has a key 502. The LUF processor 304 then schedules the key requests to the search cluster. The search cluster 320 receives a key 502 from the LUF processor 304 at the TWE 512. A key represents, for example, a field extracted from a packet header. The TWE 512 is configured to issue requests to access the tree 412 in the OCM 324 and receive corresponding responses. A tree access request includes a key used to enable the TWE 512 to walk, or traverse, the tree from a root node 432 to a possible leaf node 413. If the TWE 512 does not find an appropriate leaf node, the TWE 512 issues a no match response to the LUF processor 304. If the TWE 512 does find an appropriate leaf node, it issues a response that an appropriate leaf node is found.

The response that an appropriate leaf node is found includes, for example, a pointer to a bucket passed by the TWE 512 to the BWE 514. The BWE 514 is configured to issue requests to access buckets 414 in the OCM 324 and receive corresponding responses. The BWE 514, for example, uses the pointer to the bucket received from the TWE 512 to access one or more buckets 414 and retrieve at least one chunk pointer 418 pointing to a chunk of rules. The BWE 514 provides the retrieved at least one chunk pointer 418 to at least one RWE 516. According to at least one example, BWE 514 may initiate a plurality of rule searched to be processed by one RWE 516. However, the maximum number of outstanding, or on-going, rule searches at any point of time may be constrained, e.g., maximum of 16 rule searches. The RWE is configured to issue requests to access rule chunks 420 in the OCM 324 and receive corresponding responses. The RWE 516 uses a received chunk pointer 418 to access rule chunks stored in the OCM 324 and retrieve one or more rule chunks. The retrieved one or more rule chunks are then passed to one or more RMEs 518. An RME 518, upon receiving a chunk rule, is configured to check whether there is a match between one or more rules in the retrieved rule chunk and the field corresponding to the key.

The RME 518 is also configured to provide a response, to the BWE 514. The response is indicative of a match, no match, or an error. In the case of a match, the response may also include an address of the matched rule in the OCM 324 and information indicative of a relative priority of the matched rule. Upon receiving a response, the BWE 514 decides how to proceed. If the response is indicative of a no match, the BWE 514 continues searching bucket entries and initiating more rule searches. If at some point the BWE 514 receives a response indicative of a match, it stops initiating new rule searches and waits for any outstanding rule searches to complete processing. Then, the BWE 514 provides a response to the host processor through the LUF processor 304, indicating that there is a match between the field corresponding to the key and one or more rules in the retrieved rule chunk(s), e.g., a “match found” response. If the BWE 514 finishes searching buckets without receiving any “match found” response, the BWE 514 reports a response to the host processor through the LUF processor 304 indicating that there is no match, e.g., “no-match found” response. According to at least one example embodiment, the BWE 514 and RWE 516 may be combined into a single processing engine performing both bucket and rule chunk data searches. According to an example embodiment the RWEs 516 and the RMEs 518 may be separate processors. According to another example embodiment, the access and retrieval of rule chunks 420 may be performed by the RMEs 518 which also performs rule matching. In other words, the RMEs and the RWEs may be the same processors.

Access requests from the TWE 512, the BWE 514, or the RWE(s) are sent to the OBS module 520. The OBS module 520 is coupled to the memory banks in the OCM 324 through a number of logical, or access, ports, e.g., M ports. The number of the access ports enforce constraints on the number of access requests that may be executed, or the number of memory banks that may be accessed, at a given clock cycle. For example, over a typical logical port no more than one access request may be executed, or sent, at a given clock cycle. As such, the maximum number of access requests that may be executed, or forwarded to the OCM 324, per clock cycle is equal to M. The OBS module 520 includes a scheduler, or a scheduling module, configured to select a subset of access requests, from multiple access requests received in the OBS module 520, to be executed in at least one clock cycle and to schedule the selected subset of access requests each over a separate access port. The OBS module 520 attempts to maximize OCM usage by scheduling up to M access requests to be forwarded to the OCM 324 per clock cycle. In scheduling access requests, the OBS module 520 also aims at avoiding memory bank conflict and providing low latency for access requests. Memory bank conflict occurs, for example, when attempting to access a memory bank by more than one access request at a given clock cycle. Low latency is usually achieved by preventing access requests from waiting for a long time in the OBS module 520 before being scheduled or executed.

Upon data being accessed in the OCM 324, a response is then sent back to a corresponding engine/entity through a “Read Data Path” (RDP) component 540. The RDP component 540 receives OCM read response data and context, or steering, information from the OBS. Read response data from each OCM port is then directed towards the appropriate engine/entity. The RDP component 540 is, for example, a piece of logic or circuit configured to direct data responses from the OCM 324 to appropriate entities or engines, such as TWE 512, BWE 514, RWE 516, a host interface component (HST) 550, and a cross-bar controller (XBC) 530. The HST 550 is configured to store access requests initiated by the host processor or a respective software executing thereon. The context, or steering, information tells the RDP component 540 what to do with read data that arrives from the OCM 324. According to at least one example embodiment, the OCM 324 itself does not contain any indication that valid read data is being presented to the RDP component 540. Therefore, per-port context information is passed from the OBS module 520 to the RDP component 540 indicating to the RDP component 540 that data is arriving from the OCM 324 on the port, the type of data being received, e.g., tree data, bucket data, rule chunk data, or host data, and the destination of the read response data, e.g., TWE 512, BWE 514, RWE 516, HST 550 or XBC 530. For example, tree data is directed to TWE 512 or XBC 530 if remote, bucket data is directed to BWE 514 or XBC if remote, rule chunk data is directed to RWE 516 or XBC 530 if remote, and host read data is directed to the HST 550.

The search cluster 320 also includes the crossbar controller (XBC) 530 which is a communication interface managing communications, or transport operations, between the search cluster 320 and other search clusters through the crossbar (XBAR) 312. In other words, the XBC 530 is configured to manage pushing and pulling of data to, and respectively from, the XBAR 312.

According to an example embodiment, for rule processing, the processing engines 510 include a tree walk engine (TWE) 512, bucket walk engine (BWE) 514, rule walk engine (RWE) 516 and rule match engine (RME) 518. According to another example embodiment, rule processing is extended to external memory and the BPP 307 also includes a RWE 516 and RME 518, or a RME acting as both RWE 516 and RME 518. In other words, the rules may reside in the on-chip memory and in this case, the RWE or RME engaged by the BWE, e.g., by passing a chunk pointer, is part of the same LUE as BWE. As such, the BWE engages a “local” RWE or RME. The rules may also reside on a memory located external to the search processor 202, e.g., off-chip memory. In this case, which may be referred to as rule processing extended to external memory or, simply, “rule extension,” the bucket walk engine does not engage a local RWE or RME. Instead, the BWE sends a request message, via the MWA 303 and MBC 305, to a memory controller to read a portion, or chunk, of rules. The BWE 514 also sends a “sideband” message to the BPP 307 informing the BPP 307 that the chunk, associated with a given key, is stored in external memory.

The BPP 307 starts processing the chunk of rules received from the external memory. As part of the processing, if the BPP 307 finds a match, the BPP 307 sends a response, referred to as a lookup response or sub-tree response, to the LUF processor 304. The BPP 307 also sends a message to the LUEs component 322 informing the LUEs component 322 that the BPP 307 is done processing the chunk and the LUEs component 322 is now free to move on to another request. If the BPP 307 does not find a match and the BPP 307 is done processing the chunk, the BPP 307 sends a message to the LUEs component 322 informing the LUEs component 322 that the BPP 307 is done processing and to send the BPP 307 more chunks to process. The LUEs component 322 then sends a “sideband” message, through the MWA 303 and MBC 305, informing the BPP 307 about a next chunk of rules, and so on. For the last chunk of rules, the LUEs component 322 sends a “sideband” message to the BPP 307 informing the BPP 307 that the chunk, which is to be processed by the BPP 307, is the last chunk. The LUEs component 322 knows that the chunk is the last chunk because the LUEs component 322 knows the total size of the set of rule chunks to be processed. Given the last chunk, if the BPP 307 does not find a match, the BPP 307 sends a “no-match” response to the LUF processor 304 informing the LUF processor 304 that the BPP 307 is done with the set of rule chunks. In turn, the LUEs component 322 frees up the context, e.g., information related to the processed key request or the respective work done, and moves on to another key request.

FIG. 6A shows a block diagram illustrating an example embodiment of processing a remote access request between two search clusters. A remote access request is a request generated by an engine/entity in a first search cluster to access data stored in a second search cluster or memory outside the first search cluster. For example, a processing engine in cluster 1, 320 a, sends a remote access request for accessing data in another cluster, e.g., cluster N 320 b. The remote access request may be, for example, a tree data access request generated by a TWE 512 a in cluster 1, a bucket access request generated by a BWE 514 a in cluster 1, or a rule chunk data access request generated by a RWE 516 a or RME in cluster 1. The remote access request is pushed by the XBC 530 a of cluster 1 to the XBAR 312 and then sent to the XBC 530 b of cluster N. The XBC 530 b of cluster N then forwards the remote access request to the OBS module 520 b of cluster N. The OBS module 520 b directs the remote access request to OCM 324 b of cluster N and a remote response is sent back from the OCM 324 b to the XBC 530 b through the RDP 540 b. The XBC 530 b forwards the remote response to the XBC 530 a through the XBAR 312. The XBC 530 a then forwards the remote response to the respective processing engine in the LUEs component 322 a.

FIG. 6B shows a block diagram illustrating an example embodiment of a processing thread migration between two search clusters. Migration requests originate from a TWE 512 or BWE 514 as they relate mainly to a bucket search/access process or a tree search/access process, in a first cluster, that is configured to continue processing in a second cluster. Unlike remote access where data is requested and received from the second cluster, in processing thread migration the process itself migrates and continues processing in the second cluster. As such, information related to the processing thread, e.g., state information, is migrated to the second cluster from the first cluster. As illustrated in FIG. 6B, processing thread migration requests are sent from TWE 512 a or BWE 514 a directly to the XBC 530 a in the cluster 1, 320 a. The XBC 530 a sends the migration request through the crossbar (XBAR) 312 to the XBC 530 b in cluster N, 320 b. At the receiving cluster, e.g., cluster N 320 b, the XBC 530 b forwards the migration request to the proper engine, e.g., TWE 512 b or BWE 514 b. According to at least one example embodiment, the XBC, e.g., 530 a and 530 b, does not just forward requests. The XBC arbitrates which, among remote OCM requests, OCM response data, and migration requests, to be sent at a clock cycle.

FIG. 7 shows an example hardware implementation of the OCM 324 in a cluster 320. According to the example implementation shown in FIG. 7, the OCM includes a plurality, e.g., 16, single-ported memory banks 705 a-705 p. Each memory bank, for example, includes 4096 memory rows, each of 256 bits width. A person skilled in the art should appreciate that the number, e.g., 16, of the memory banks and their storage capacity are chosen for illustration purposes and should not be interpreted as limiting. Each of the memory banks 705 a-705 p is coupled to at least one input multiplexer 715 a-715 p and at least one output multiplexer 725 a-725-p. Each input multiplexer, among the multiplexers 715 a-715 p, couples the input logical ports 710 a-710 d to a corresponding memory bank among the memory banks 705 a-705 p. Similarly, each output multiplexer, among the multiplexers 725 a-725 p, couples the output logical ports 720 a-720 d to a corresponding memory bank among the memory banks 705 a-705 p.

The input logical ports 710 a-710 d carry access requests' data from the OBS module 520 to respective memory banks among the memory banks 705 a-705 p. The output logical ports 720 a-720 d carry access responses' data from respective memory banks, among the memory banks 705 a-705 p, to RDP component 540. Given that the memory banks 705 a-705 p are single-ported, at each clock cycle a single access is permitted to each of the memory banks 705 a-705 p. Also given the fact that there are four input logical/access ports, a maximum of four requests may be executed, or served, at a given clock cycle because no more than one logical port may be addressed to the same physical memory bank at the same clock cycle. For a similar reason, e.g., four output logical/access ports, a maximum of four responses may be sent out of the OCM 324 at a given clock cycle. An input multiplexer is configured to select a request, or decide which request, to access the corresponding physical memory bank. An output multiplexer is configured to select an access port on which a response from a corresponding physical memory bank is to be sent. For example, an output multiplexer may select an output logical port, to send a response, corresponding to an input logical port on which the corresponding request was received. A person skilled in the art should appreciate that other implementations with more, or less, than four ports may be employed.

According to an example embodiment, an access request is formatted as an 18 bit tuple. Among the 18 bits, two bits are used as wire interface indicating an access instruction/command, e.g., read, write, or idle, four bits are used to specify a memory bank among the memory banks 705 a-705 p, and 12 bits are used to identify a row, among the 4096 rows, in the specified memory bank. In the case of a “write” command, 256 bits of data to be written are also sent to the appropriate memory bank. A person skilled in the art should appreciate that such format/structure is appropriate for the hardware implementation shown in FIG. 7. For example, using 4 bits to specify a memory bank is appropriate if the total number of memory banks is 16 or less. Also the number of bits used to identify a row is correlated to the total number of rows in each memory bank. Therefore, the request format described above is provided for illustration purpose and a person skilled in the art should appreciate that many other formats may be employed.

The use of multi-banks as suggested by the implementation in FIG. 7, enables accessing multiple physical memory banks per clock cycle, and therefore enables serving, or executing, more than one request/response per clock cycle. However, for each physical memory bank a single access, e.g., read or write, is allowed per clock cycle. According to an example embodiment, different types of data, e.g., tree data, bucket data, or rule chunk data, are stored in separate physical memory banks. Alternatively, a physical memory bank may store data from different types, e.g., tree data, bucket data, and rule chunk data. Using single-ported physical memory banks leads to more power efficiency compare to multi-port physical memory banks. However, multi-port physical memory banks may also be employed.

Processing operations, e.g., tree search, bucket search, or rule chunk search, may include processing across memory clusters. For example, a processing operation running in a first memory cluster may require accessing data stored in one or more other memory clusters. In such a case, a remote access request may be generated, for example by a respective processing engine, and sent to at least one of the one or more other memory clusters and a remote access response with the requested data may then be received. Alternatively, the processing operation may migrate to at least one of the one or more other memory clusters and continue processing therein. For example, a remote access request may be generated if the size of the data to be accessed from another memory cluster is relatively small and therefore the data may be requested and acquired in relatively short time period. However, if the data to be accessed is of relatively large size, then it may be more efficient to proceed with a processing thread migration where the processing operation migrates and continue processing in the other memory cluster. The transfer of data, related to a processing operation, between different memory clusters is referred to hereinafter as a transport operation. Transport operations, or transactions, include processing thread migration operation(s), remote access request operation(s), and remote access response operation(s). According to an example embodiment, transport operations are initiated based on one or more instructions embedded in the OCM 324. When a processing engine, fetching data within the OCM 324 as part of a processing operation, reads an instruction among the one or more embedded instructions, the processing engine responds to the read instruction by starting a respective transport operation. The instructions are embedded, for example, by software executed by the host processor, 204, 214, 228, 242, 244, such as the software compiler 404.

The distinction between remote access request/response and processing thread migration is as follows: When a remote request is made, a processing engine is requesting and receiving the data (RCDS) that is on a remote memory cluster to the memory cluster where work is being executed by the processing engine. The same processing engine in a particular cluster executes both local data access and remote data access. For processing thread migrations, work is partially executed on a first memory cluster. The context, e.g., state and data, of the work is then saved, packaged and migrated to a second memory cluster where data (RCDS) to be accessed exists. A processing engine in the second memory cluster picks up the context and continues with the work execution.

FIG. 8A shows a block diagram illustrating an overview of the XBC 530, according to at least one example embodiment. The XBC 530 is an interface configured to manage transport operations between the corresponding memory, or search, cluster and one or more other memory, or search, clusters through the XBAR 312. The XBC 530 includes a transmitting component 845 configured to manage transmitting transport operations from the processing engines 510 or the OCM 324 to other memory, or search, cluster(s) through the XBAR 312. The XBC 530 also includes a receiving component 895 configured to manage receiving transport operations, from other memory, or search, cluster(s) through the XBAR 312, and directing the transport operations to the processing engines 510 or the OCM 324. The XBC 530 also includes a resource, or credit, state manager 850 configured to manage states of resources allocated to the corresponding memory cluster in other memory clusters. Such resources include, for example, memory buffers in the other memory clusters configured to store transport operations data sent from the memory cluster including the resource state manager 850. The transmitting component 845 may be implemented as a logic circuit, processor, or the like. Similarly, the receiving component 895 may be implemented as a logic circuit, processor, or the like.

FIGS. 8B and 8C show logical diagrams illustrating an example implementation of the transmitting component 845, of the XBC 530, and the resource state manager 850. The transmitting component 845 is coupled to the OCM 324 and the processing engines 510, e.g., TWEs 512, BWEs 514, and RWEs 516 or RMEs 518, as shown in the logical diagrams. Among the processing engines 510, the TWEs 512 make remote tree access requests, the BWEs 514 make remote bucket access requests, and the RWEs 516 make remote rule access requests. The remote requests are stored in one or more first in first out (FIFO) buffers 834 and then pushed into per-destination FIFO buffers, 806 a . . . 806 g, to avoid head-of-line blocking. The one or more FIFO buffers 834 may include, for example, a FIFO buffer 832 for storing tree access requests, FIFO buffer 834 for storing bucket access requests, FIFO buffer 836 for storing rule chunk access requests, and an arbitrator/selector 838 configured to select remote requests from the different FIFO buffers to be pushed into the per-destination FIFO buffers, 806 a-806 g. Similarly, remote access responses received from the OCM 324 are stored in a respective FIFO buffer 840 and then pushed into a per-destination FIFO buffers, 809 a-809 g, to avoid head-of-line blocking.

The remote requests for all three types of data, e.g., tree, bucket and rule chunk, are executable in a single clock cycle. The remote access responses may be variable length data and as such may be executed in one or more clock cycles. The size of the remote access response is determined by the corresponding remote request, e.g., the type of the corresponding remote request or the amount of data requested therein. Execution time of a transport operation, e.g., remote access request operation, remote access response, or processing thread migration operation, refers herein to the time duration, e.g., number of clock cycles, needed to transfer data associated with transport operation between a memory cluster and the XBAR 312. With respect to a transport operation, a source memory cluster, herein, refers to the memory cluster sending the transport operation while the destination memory cluster refers to the memory cluster receiving the transport operation.

The TWEs 512 make tree processing thread migration requests, BWEs 514 make bucket processing thread migration requests. In the following, processing thread migration may be initiated either by TWEs 512 or BWEs 514. However, according to other example embodiments the RWEs 516 may also initiate processing thread migrations. When TWEs 512 or BWEs 514 make processing thread migration requests, the contexts of the corresponding processing threads are stored in per-destination FIFO buffers, 803 a-803 g. According to an example embodiment, destination decoders, 802, 805, and 808, are configured to determine the destination memory cluster for processing thread migration requests, remote access requests, and remote access responses, respectively. Based on the determined destination memory cluster, data associated with the respective transport operation is then sent to a corresponding per-destination FIFO buffer, e.g., 803 a-803 g, 806 a-806 g, and 809 a-809 g. The logic diagrams in FIGS. 8B and 8C assume a super cluster 310 including eight memory, or search, clusters 320. As such, each transport operation in a particular memory cluster may be destined to at least one of seven memory clusters referred to in the FIGS. 8B and 8C with the letters a . . . g.

According to an example embodiment, a per-destination arbitrator, 810 a-810 g, is used to select a transport operation associated with the same destination memory cluster. The selection may be made, for example, based on per-type priority information associated with the different types of transport operations. Alternatively, the selection may be made based on other criteria. For example, the selection may be performed based on a sequential alternation between the different types of transport operations so that transport operations of different types are treated equally. In another example embodiment, data associated with a transport operation initiated in a previous clock cycle may be given higher priority by the per-destination arbitrators, 810 a-810 g. As shown in FIG. 8C, each per-destination arbitrator, 810 a-810 g, may include a type selector, 812 a-812 g, a retriever, 814 a-814 g, and a destination FIFO buffer, 816 a-816 g. The type selector, 812 a-812 g, selects a type of a transport operation and passes information indicative of selected type to the retriever, 814 a-814 g, which retrieves the data at the head of a corresponding per-destination FIFO buffer, e.g., 803 a-803 g, 806 a-806 g, or 809 a-809 g. The retrieved data is then stored in the destination FIFO buffer, 816 a-816 g.

The transmitting component 845 also includes an arbitrator 820. The arbitrator 820 is coupled to the resource state manager 850 and receives or checks information related to the states of resources, in destination memory clusters, allocated to the source memory cluster processing the transport operations to be transmitted. The arbitrator 820 is configured to select data associated with at least one transport operation, or transaction, among the data provided by the arbitrators, 810 a-810 g, and schedule the at least one transport operation to be transported over the XBAR 312. The selection is based at least in part on the information related to the states of resources and/or other information such as priority information. For example, resources in destination memory clusters allocated to the source memory cluster are associated with remote access requests and processing thread migrations but no resources are associated with remote access responses. In other words, for a remote access response a corresponding destination memory cluster is configured to receive the remote access response at any time regardless of other processes running in the destination memory cluster. For example, resources in the destination memory clusters allocated to the source memory cluster include buffering capacities for storing data associated with transport operations received at the destination memory clusters from the source memory cluster. As such no buffering capacities, at the destination memory clusters, are associated with remote access responses.

Priority information may also be employed by the arbitrator 820 in selecting transport operations or corresponding data to be delivered to respective destination memory clusters. Priority information, for example, may prioritize transport operations based on respective types. The arbitrator may also prioritize data associated with transport operations that were initiated at a previous clock cycle but are not completely executed. Specifically, data associated with a transport operation executable in multiple clock cycles and initiated in a previous clock cycle may be prioritized over data associated with transport operations to be initiated. According to at least one example embodiment, transport operations, or transactions, executable in multiple clock cycles are not required to be delivered in back to back clock cycles. Partial transport operations, or transactions, may be scheduled to be transmitted to effectively use the XBAR bandwidth. The arbitrator 820 may interleave partial transport operations, corresponding to different transport operations, over consecutive clock cycles. At the corresponding destination memory cluster, the transport operations, or transactions, are pulled from the XBAR 312 based on transaction type, transaction availability from various source ports to maximize the XBAR bandwidth.

The selection of transport operations, or partial transport operations, by the arbitrator 820 may also be based on XBAR resources associated with respective destination memory clusters. XBAR resources include, for example, buffering capacities to buffer data to be forwarded to respective destination memory clusters. As such, the resource state manager 850 in a first memory cluster keeps track of XBAR resources as well as the resources allocated to the first memory cluster in other memory clusters.

According to an example embodiment, the arbitrator 820 includes a destination selector 822 configured to select a destination FIFO buffer, among the destination FIFO buffers 816 a-816 g, from which data to be retrieved and forwarded, or scheduled to be forwarded, to the XBAR 312. The destination selector passes information indicative of the selected destination to a retriever 824. The retriever 824 is configured to retrieve transport operation data from the respective destination FIFO buffer, 816 a-816 g, and forward the retrieved transport operation data to the XBAR 312.

The resource state manager 850 includes, for example, a database 854 storing a data structure, e.g., a table, with information indicative of resources allocated to the source memory cluster in the other clusters. The data structure may also include information indicative of resources in the XBAR 312 associated with destination memory clusters. The resource state manager 850 also includes a resource state logic 858 configured to keep track and update state information indicative of available resources that may be used by the source memory cluster. In other words, the resource state logic 858 keeps track of free resources allocated to the sources memory cluster in other memory clusters as well as free resources in the XBAR 312 associated with the other memory clusters. Resource state information may be obtained by updating, e.g., incrementing or decrementing, the information indicative of resources allocated to the source memory cluster in the other clusters and the information indicative of resources in the XBAR 312 associated with destination memory clusters. Alternatively, state information may be stored in a separate data structure, e.g., another table. Updating the state information is, for example, based on information received from the other memory clusters, the XBAR 312, or the arbitrator 820 indicating resources being consumed or freed in at least one destination resources or the XBAR 312.

According to an example embodiment, a remote access request operation is executed in a single clock cycle as it involves transmitting a request message. A processing thread migration is typically executed in two or more clock cycles. A processing thread migration includes the transfer of data indicative of the context, e.g., state, of the search associated with the processing thread. A remote access response is executed in one or more clock cycle depending on the amount of data to be transferred to the destination memory cluster.

FIGS. 8D and 8E show logical diagrams illustrating an example implementation of the receiving component 895, of the XBC 530. According to at least one example embodiment, the receiving component 895, e.g., in a first memory cluster, includes a type identification module 860. The type identification module 860 receives information related to transport operations destined to the first memory cluster with data in the XBAR 312. The received information, for example, includes indication of the respective types of the transport operations. According to the example implementation shown in FIG. 8E, the type identification module 860 includes a source decoder 862 configured to forward the received information, e.g., transport operation type information, to per-source FIFO buffers 865 a-865 g also included in the type identification module 860. For example, received information associated with a given source memory cluster is forwarded to a corresponding per-source memory FIFO buffer. An arbitrator 870 then acquires the information stored in the per-source FIFO buffers, 865 a-865 g, and selects at least one transport operation for which data is to be retrieved from the XBAR 312. Data corresponding to the selected transport operation is then retrieved from the XBAR 312.

If the selected transport operation is a remote access request, the retrieved data is stored in the corresponding FIFO buffer 886 and handed off to the OCM 324 to get the data. That data is sent back as remote response to the requesting source memory cluster. If the selected transport operation is a processing thread migration, the retrieved data is stored in one of the corresponding FIFO buffers 882 or 884, to be forwarded later to a respective processing engine 510. The FIFO buffers 882 or 884 may be a unified buffer managed as two separate buffers enabling efficient management of cases where processing thread migrations of one type are more than processing thread migrations of another type, e.g., more tree processing thread migrations than bucket processing thread migrations. When a processing engine handling processing thread migration of some type, e.g., TMIG or BMIG, becomes available respective processing thread migration context, or data, is pulled from the unified buffer and sent to the processing engine for the work to continue in this first memory cluster. According to at least one example embodiment, one or more processing engines in a memory cluster receiving migration work are reserved to process received migrated processing threads. When a remote access response operation is selected, the corresponding data retrieved from the XBAR 312 is forwarded directly to a respective processing engine 510. Upon forwarding the retrieved data to the OCM or a processing engine 510, an indication is sent to the resource state manager 850 to cause updating of corresponding resource state(s).

In the example implementation shown in FIG. 8E, the arbitrator 870 includes first selectors 871-873 configured to select a transport operation among each type and a second selector 875 configured to select a transport operation among the transport operations of different types provided by the first selectors 871-873. The second selector 875 sends indication of the selected transport operation to the logic operators 876 a-876 c, which in turn pass only data associated with the selected transport operation. The example receiving component 895 shown in FIG. 8D also includes a logic operator, or type decoder, 883 configured direct processing thread migration data to separate buffers, e.g., 882 and 884, based on processing thread type, e.g., tree or bucket. Upon forwarding a transport operation to the OCM 324 or a respective processing engine 510, a signal is sent to a resource return logic 852. The resource return logic 852 is part of the resource state manager 850 and is configured to cause updating of resource state information.

FIG. 9A is a block diagram illustrating an example implementation of the XBAR 312. A person skilled in the art should appreciate that the XBAR 312 as described herein is an example of an interface device coupling a plurality of memory clusters. In general, different interface devices may be used. The example implementation shown in FIG. 9A is an eight port fully-buffered XBAR that is constructed out of modular slices 950 a-950 d. For example, the memory clusters are arranged in two rows, e.g., north memory clusters, 320 a, 320 c, 320 e, and 320 g, are indexed with even numbers and south memory clusters, 320 b, 320 d, 320 f, and 320 h, are indexed with odd numbers. The XBAR 312 is constructed to connect these clusters. To match the cluster topology, the example XBAR 312 in FIG. 9A is built as a 2×4 (8-port) XBAR 312. Each slice connects a pair of North-South memory clusters to each other and to its neighboring slice(s).

FIG. 9B is a block diagram illustrating implementation of two slices, 950 a and 950 b, of the XBAR 312. Each slice is built using half-slivers 910 and full-slivers 920. The half-slivers 910 and the full-slivers 920 are, for example, logic circuits used in coupling memory clusters to each other. For an N-port XBAR 312, each slice contains N−2 full-slivers 920 and 2 half-slivers 910. The full-slivers 920 correspond to memory cluster ports that are used to couple memory clusters 320 belonging to distinct slices 950. For the slice 950 a, for example, full-slivers 920 correspond to ports 930 c to 930 h which couple memory clusters in the slice 950 a to the memory clusters 320 b-320 d, respectively, in other slices 950. For the memory cluster ports coupling memory cluster within the same slice, the slivers are optimized to half-slivers 910. For the slice 950 a, for example, half-slivers correspond to ports 930 a and 930 b.

FIG. 9C shows an example logic circuit implementation of a full-sliver 920. The full-sliver 920 contains two FIFO buffers, 925 a and 925 b, for storing data from other ports through a neighboring slice. One FIFO buffer, e.g., 925 a, is for storing data destined to the north memory cluster and one FIFO buffer, e.g., 925 b, is for storing the data destined to the south memory cluster. The control (GRQs) signals 922 a and 922 b identify which port the data is destined to. The data (GRFs) 921 is pushed into the appropriate full-sliver FIFO 925 a or 925 b. For example, when data from the memory cluster_320 c is destined to the memory cluster_320 b, GRQ2 and GRF2 will signal to the south FIFO buffer 925 b of the full sliver SLV2 in slice 950 a to capture and keep the data until it is demanded by the memory cluster 320 b. Continuing with the same example, if data was destined to the memory cluster_320 a, GRQ2 will signal the north FIFO buffer 925 a the full sliver SLV2 in slice 950 a to capture and keep the data until demanded by the memory cluster_320 a.

FIG. 9D shows an example logic circuit implementation of a half-sliver 910. Each half-sliver 910 contains one FIFO buffer 925 for storing data from one of two memory clusters within a given slice. The data in each half-sliver 910 is meant for the opposite memory cluster in the same slice. For example, in the slice 950 a, the half-sliver HSLV0 gets data (GRF1) from the memory cluster_320 a and is destined to the memory cluster_320 b.

When a memory cluster decides to fetch the data from a particular FIFO buffer, e.g., 925, 925 a, or 925 b, it sends a pop signal, 917, 927 a, or 927 b, to that FIFO buffer. When the FIFO buffer, e.g., 925, 925 a, or 925 b, is not selected by the memory cluster the logic AND operator 914, 924 a, or 924 b, outputs zeroes. An OR operator, e.g., 916, 926 a, or 926 b, in each sliver is applied to the data resulting in a chain of OR operators either going north or going south. According to an example embodiment, one clock cycle delay between pop signal and data availability at the memory cluster that's pulling the data.

The XBAR 312 is the backbone for transporting various transport transactions, or operations, such as remote requests, remote responses, and processing thread migrations. The XBAR 312 provides the transport infrastructure, or interface. According to at least one example embodiment, transaction scheduling, arbitration and flow control is handled by the XBC 530. In any given clock cycle multiple pairs of memory clusters may communicate. For example, the memory cluster 320 a communicates with the memory cluster 320 b, the memory cluster 320 f communicates to the memory cluster 320 c, etc. The transfer time for transferring a transport operation, or a partial transport operation, from a first memory cluster to a second memory cluster is fixed with no queuing delays in the XBAR 312 or any of the XBCs of the first and second memory clusters. However, in the case of queuing delays, the transfer time, or latency, depends on other transport operations, or partial transport operations, in the queue and the arbitration process.

Resources are measured in units, e.g., “credits.” For example, a resource in a first memory cluster, e.g., destination memory cluster, allocated to a second memory cluster, e.g. source memory cluster, represented by one credit corresponds to one slot in a respective buffer, e.g., 882, 884, or 886. According to another example, one credit may represent storage capacity equivalent to the amount of data transferrable in a single clock cycle. XBAR resources refer, for example, to storage capacity of FIFO buffers, e.g., 915, 925 a, 925 b, in the XBAR. In yet another example, one credit corresponds to storage capacity for storing a migration packet or message.

The XBAR 312 carries single- and multi-cycle packets, and/or messages, from one cluster to another over, for example, a 128 bit crossbar. These packets, and/or messages, are for either remote OCM access or processing thread migration. Remote OCM access occurs when a processing thread, e.g., the TWE and/or BWE, on one cluster encounters Rule Compiled Data Structure (RCDS) image data that redirects a next request to a different memory cluster within the same super-cluster. Processing thread migration occurs for two forms of migration, namely, a) Tree-Walk migration and b) Bucket-Walk migration. In either case, the processing thread context, e.g., details of the work done so far and where to start working, for the migrated thread is transferred to a different memory cluster within the same super-cluster, which continues processing for the thread.

FIGS. 10A and 10B show two example tables storing resource state information in terms of credits. The stored state information is employed in controlling the flow of transport transactions. Both tables, in FIGS. 10A and 10B, illustrate two examples of resource credits allocated to the memory cluster indexed with 0 in the memory clusters indexed with 1 through 7. In FIG. 10A, the first column shows unified migration, the second column shows remote request credits and the third column shows XBAR credits allocated to the memory cluster indexed with 0. In FIG. 10B, the migration credits are separated based on the type of processing thread migration, e.g., tree processing thread migration and bucket processing thread migration. Migration credits track the migration buffer(s) availability at a particular destination. Remote request credits track the remote request buffer(s) availability at the destination. XBAR credit tracks the resources inside the XBAR to a particular destination. There are no separate credits for responses. The response space is pre-allocated in the respective engine.

When a remote access request is sent from a first memory cluster, e.g., a source cluster, to a second memory cluster, e.g., destination cluster, the resource state manager 850 of the first memory cluster decrements, e.g., by a credit, the credits defining the remote request resources allocated to the first memory cluster in the second memory cluster. The resource state manager 850 may also decrement, e.g., by a credit, the credits defining the state of XBAR resources associated with the second memory cluster and allocated to the first memory cluster. When the remote access request is passed from the XBAR 312 to the destination memory cluster, the resource state manager 850, at the source memory cluster, receives a signal from the XBAR 312 indicating the resource represented by the decremented credit is now free. The resource state manager 850, in the first cluster, then increments the state of the XBAR resources associated with the second memory cluster and allocated to the first memory cluster by a credit. When the corresponding remote access response is received from the second memory cluster and is passed to a corresponding engine in the first cluster, a signal is sent to the resource return logic 852 which in turn increments, e.g., by a credit, the state of resources allocated to the first memory cluster in the second memory cluster.

When a processing thread is migrated from the first memory cluster to the second memory cluster, the resource state manger 850 of the first memory cluster decrements, e.g., by a credit, the credits defining the migration resources allocated to the first memory cluster in the second memory cluster. The resource state manager 850 of the first memory cluster may also decrement, e.g., by a credit, the credits defining the state of XBAR resources associated with the second memory cluster and allocated to the first memory cluster. When the migrated processing thread is passed from the XBAR 312 to the destination memory cluster, the resource state manager 850 of the first memory cluster receives a signal from the XBAR 312 indicating the resource represented by the decremented credit is now free. The resource state manager 850, in the first memory cluster, then increments the state of the XBAR resources associated with the second memory cluster and allocated to the first memory cluster by a credit. When the migrated processing thread is passed to a corresponding engine, a signal is sent to the resource return logic 852 of the second memory cluster, which in turn forwards the signal to the resource state manager 850 of the first memory cluster. The resource state manager 850 of the first memory cluster then increments, e.g., by a credit, the migration resources allocated to the first memory cluster in the second memory cluster. Decrementing or incrementing migrations credits may be performed based on the type of processing thread being migrated, e.g., tree processing thread or bucket processing thread, as shown in FIG. 10B.

FIGS. 11A to 11C illustrate examples of interleaving transport operations and partial transport operations over consecutive clock cycles. In FIG. 11A, a processing thread migration is executed in at least four non-consecutive clock cycles with remote access requests executed in between. Specifically, the processing thread migration is executed over the clock cycles indexed with 0, 2, 3 and 5 while two remote access requests are executed, respectively, over the clock cycles indexed with 1 and 4. The interleaved transport operations in FIG. 11A are executed by a source memory cluster destined to the same memory cluster. FIG. 11B shows an example of interleaving transport operations executed by a source memory cluster destined to two destination memory clusters, e.g., indexed with 0 and 1. FIG. 11C shows an example of interleaving transport operations and partial transport operations executed by a destination memory cluster. Specifically, a remote access response, received from the memory cluster indexed with 0, is executed over the clock cycles indexed with 0, 1, and 3, while two remote access requests destined to two distinct memory clusters over the clock cycles indexed with 2 and 4.

FIG. 12A shows a flowchart illustrating a method of managing transport operations between a source memory cluster and one or more other memory clusters performed by the XBC 530. Specifically the method is performed by the XBC in a source memory cluster. At block 1210 at least one transport operation from one or more transport operations is selected, at a clock cycle in the source memory cluster, the at least one transport operation is destined to at least one destination memory cluster based at least in part on priority information associated with the one or more transport operations or current states of available processing resources allocated to the source memory cluster in each of a subset of the one or more other clusters. At block 1220, the transport of the selected at least one transport operation is initiated. The one or more transport operations are received from processing engines 510 and/or OCM 324. The method may be implemented through an implementation of the XBC as shown in FIGS. 8B and 8C. However, a person skilled in the art should appreciate that the method may be implemented a different implementation of the XBC. For example, the priority information may be based on the type, latency, or destination, of the one or more transport operations. The selection may further be based on XBAR resources associated with the destination memory cluster.

FIG. 12B shows a flowchart illustrating another method of managing transport operations between a destination memory cluster and one or more other memory clusters performed by the XBC 530. Specifically the method is performed by the XBC in a destination memory cluster. At block 1260, information related to one or more transport operations with related data buffered in an interface device is received, in the source memory cluster, the interface device coupling the destination memory cluster to the one or more other memory clusters. At block 1270, at least one transport operation, from the one or more transport operations, is selected to be transported to the destination memory cluster based at least in part on the received information. At block 1280 the transport of the selected at least one transport operation is initiated.

According to at least one example embodiment, resource credits are assigned to memory clusters by software of the host processor, e.g., 204, 214, 228, 242, or 244. The software may be, for example, the software compiler 404. The assignment resource credits may be performed, for example, when the search processor 202 is activated or reset. The assignment of the resource credits may be based on the type of data stored in each memory cluster, the expected frequency of accessing the stored data in each memory cluster, or the like.

FIG. 13 shows a flowchart illustrating a method of assigning resources used in managing transport operations between a first memory cluster and one or more other memory clusters. At block 1310, information indicative of allocation of a subset of processing resources in each of the one or more other memory clusters to the first memory cluster is received, for example, by the resource state manager 850 of the first memory cluster. At block 1320, information indicative of resources allocated to the first cluster is stored in the first memory cluster, specifically in the respective resource state manager 850. The allocated processing resources may be stored as credits. The processing resources may be allocated per type of transport operations as previously shown in FIGS. 10A and 10B. The allocated processing resources may be stored in the form of a table or any other data structure. At block 1330, the information indicative of resources allocated to the first memory cluster, stored in the resource state manager 850, is then used to facilitate managing of transport operations between the first memory cluster and the one or more other memory clusters. For example, the stored information is used as resource state information indicative of availability of the allocated processing resources to the first memory cluster and is provided to the arbitrator 820 to manage transport operations between the first memory cluster and the one or more other memory clusters. The resource state information is updated in real time, as described above, to reflect which among the processing resources are free and which are in use. The processing resources represent, for example, buffering capacities in the each memory cluster, and as such the sum of processing resources in a given memory cluster allocated to other memory clusters is equal to or less than the total number of respective processing resources of the given memory cluster.

The host processor, e.g., 204, 214, 228, 242, or 244, may modify allocation of processing resources to the first memory cluster on the fly. For example, the host processor may increase or decrease the processing resources, or number of credits, allocated to the first memory cluster in a second memory cluster. In reducing processing resources, e.g., number of migration resources, allocated to the first memory cluster in the second memory cluster, the host processor indicates to the search processor a new value of processing resources, e.g., number of credits, to be allocated to the first memory cluster in the second memory cluster. The search processor determines, based on the state information, whether a number of free processing resources allocated to the first memory cluster in the second memory cluster is less than a number of processing resources to be reduced. Specifically, such determination may be performed by the resource state manager 850 in the first memory cluster. For example, let 5 credits be allocated to the first memory cluster in the second memory cluster, and the host processor, e.g., 204, 214, 228, 242, or 244, decides to reduce the allocated credits by 3 so that the new allocated credits would be 2. The host processor sends the new credits value, e.g., 2, to the search processor 202. The resource state manager 850 in the first memory cluster checks whether the current number of free credits, e.g., m, that are allocated to the first memory cluster from the second memory cluster is less than the number of credits to be reduce, e.g., 3. Upon determining that the number of free processing resources, e.g., m, is less than the number of processing resources to be reduced, e.g., 3, The XBC 530 in the first memory cluster blocks, initiation of new transport operations between the first memory cluster and the second memory cluster until the number of free processing resources, e.g., m, allocated to the first memory cluster in the second memory cluster is equal to or greater than the number of resource to be reduced. That is, the transfer of transport operations between the first and second memory clusters are blocked until, for example, m≧3. According to one example, only initiation of transport of new transport operations is blocked. According to another example, initiation of transport of new transport operations and partial transport operation is blocked. Once the number of free processing resources, e.g., m, allocated to the first memory cluster in the second memory cluster is equal to or greater than the number of resource to be reduced, the information indicative of allocated processing resources is updated, for example, by the resource state manager 850 in the first memory cluster to reflect the reduction, e.g., changed from 5 to 2. In another example, the checking may be omitted and the blocking of transport operations and partial transport operations may be applied until all allocated credits are free and then the modification is applied.

In increasing the number of processing resources allocated to the first memory cluster from the second memory cluster, the host processor determines whether a number of non-allocated processing resources, in the second memory cluster, is larger than or equal to a number of processing resources to be increased. For example if the number of allocated processing resources is to be increased from 5 to 8 in the first memory cluster, the number of non-allocated resources in the second memory cluster is compared to 3, i.e., 8-5. Upon determining that the number of non-allocated processing resources, in the second memory cluster, is larger than or equal to the number of processing resources to be increased, the host processor sends information, to the search processor 202, indicative of changes to be made to processing resources allocated to the first memory cluster from the second memory cluster. Upon the information being received by the search processor 202, the resource state manager 850 in the first memory cluster modifies the information indicative of allocated processing resources to reflect the increase in processing resources, in the second memory cluster, allocated to the first memory cluster. The resource state manager then uses the updated information to facilitate management of transport operations between the first memory cluster and the second memory cluster. According to another example, the XBC 530 of the first memory cluster may apply blocking of transport operations and partial transport operations both when increasing or decreasing allocated processing resources.

FIG. 14 shows a flow diagram illustrating a deadlock scenario in processing thread migrations between two memory clusters. Assume two migration credits are allocated to memory cluster 320 a from memory cluster 320 b and two migration credits are allocated to the memory cluster 320 b from the memory cluster 320 a. Also assume that a single processing engine is handling migration work in each of the memory clusters 320 a and 320 b. Two processing threads, 1410 and 1420, are migrated from the memory cluster 320 a to 320 b and two other processing threads, 1415 and 1425, are migrated from the memory cluster 320 b to 320 a. The processing threads 1410 and 1420 want to migrate back to the memory cluster 320 a, while the processing threads 1415 and 1425 want to migrate back to the memory cluster 320 b. Also the processing thread 1430 wants to migrate to the memory cluster 320 b and the processing thread 1435 wants to migrate to the memory cluster 320 a. However each memory cluster, 320 a or 320 b, can handle a maximum of three processing threads at any point in time, e.g., one by the processing engine and two in the buffers indicated by the credits. Given that there are three processing threads in each memory cluster, none of the processing threads, 1410, 1415, 1420, 1425, 1430, or 1435, can migrate. As such, a deadlock occurs with none of the migration works proceeding. The deadlock is mainly caused by allowing migration loops where a processing may migrate back to memory cluster that it migrated from previously.

According to an example embodiment, the deadlock may be avoided by limiting the number of processing threads, of a given type, being handled by a super cluster at any given point of time. Regardless of the number of memory clusters, e.g., N, in a super cluster, if a processing thread may migrate to any memory cluster in the super cluster, or in group of memory clusters, then there is a possibility that all processing threads in the super cluster may end up in two memory clusters of the super cluster, that is similar to the case of FIG. 14. Consider that each memory cluster has k processing engines for processing migration work of the given type and that each destination memory cluster has M migration credits, e.g., for migration work of the given type, to be distributed among N−1 memory clusters. The maximum number of processing threads, of a given type, that may be handled by the super cluster without potential deadlock is defined as:

${W_{\max} = {{\left( {{{Int}\left( \frac{M}{N - 1} \right)} + k} \right)*2} - 1}},$ where “Int” is a function providing the integer part of a number.

For example, let the number of processing engines for processing migration work of the given type per memory cluster be k=16. Let the number of total credits, for migration of the given type, in any destination memory cluster be M=15 and the total number of memory cluster in the super cluster, or the group of clusters, be N=4. As such the number of migration credits allocated to any source memory cluster in any destination memory cluster is 15 divided by (4-1), which is equal to 5. According to the equation above, the maximum number of processing threads that the super cluster may handle is 41. Applying the example of processing thread ending up distributed between only two memory clusters as in FIG. 14, then a first memory cluster, having 16 processing engines and 5 migration credits, may end up with 21 processing threads. That is, the 16 processing engines and the buffering capacity represented by the 5 credits are being consumed. A second memory cluster, having 16 processing engines and 5 migration credits, then ends up with the 20 other processing threads. As such a processing thread may migrate from the first memory cluster to the second memory. Given that any processing thread may either finish processing completely, migrate, or transforms into a different type of processing thread, e.g., from tree processing thread to bucket processing thread, then at a given point of time a processing thread in the first memory cluster would either transform into a processing thread of different type, finish processing completely and vanish, or migrate to the second memory cluster. In each of these cases it would become possible for a processing thread in the second memory cluster to migrate to the first memory cluster. Therefore, with such deadlock is avoided. However, if the total number of migration thread is more than the maximum indicated by the equation above, a potential deadlock may occur if the total processing threads end up being distributed between two clusters with all the engines and the migration credits therein being consumed.

FIG. 15 shows graphical illustration of another approach to avoid deadlock. The idea behind approach to avoid deadlocks is to prevent any migrations loops where a migrating processing thread may migrate to a memory cluster from which it previously migrated. In the example shown in FIG. 15, migration of four different processing threads, 1510, 1520, 1530, and 1540, across the memory clusters 320 a-320 d are illustrated, with the memory cluster 320 a assigned as a drain, or sink, memory cluster. A sink, or drain, memory cluster prevents a processing thread that migrated to it from another memory cluster to migrate out. In addition, a processing thread that migrated to a particular memory cluster may not migrate to another memory cluster from which other processing threads, e.g., of the same type, migrate to the particular memory cluster and therefore preventing migration loops. In other words, migrated processing threads may migrate to a sink memory cluster or memory cluster in a path to a sink memory cluster. A path to a sink memory cluster may not have structural migration loops. As illustrated in FIG. 15, such design, of migrations, prevent structural migration loops from occurring.

Contrary to migrated work, new work that originated in a particular memory cluster but did not migrate yet, may migrate to any other memory cluster even if the particular memory cluster is a sink memory cluster. Further, at least one processing engine is reserved to handle migration work in memory clusters receiving migration work.

FIG. 16 is a flowchart illustrating a method of managing processing thread migrations within a plurality of memory clusters. According to at least one example embodiment, instructions indicative of processing thread migrations are embedded at block 1610, in memory components of the plurality of memory clusters. Such instructions are, for example, received from the host processor in the search processor 202 and embedded by the latter in memory components of the plurality of memory clusters of the same search processor. When a processing thread, fetching data in the OCM of a first memory cluster encounters one of such instructions, the corresponding processing engine make a migration request to migrate to a second memory cluster indicated in the encountered instruction. At block 1620, data, configured to designate a particular memory cluster as a sink memory cluster, is stored in one or more memory components of the particular memory cluster. The particular memory cluster is one among the plurality of memory clusters of the search processor 202.

A sink memory cluster may be designed, for example, through the way the data to be fetched by processing engines is stored across different memory clusters and by not embedding any migration instructions in any of the memory components of the sink memory cluster. In other words, by distributing data to be fetched in a proper way between the different memory clusters, a sink memory cluster stores all the data that is to be accessed by a processing thread that migrated to the sink memory cluster. Alternatively, if some data, that is to be accessed by a processing thread that migrated to the sink memory cluster, is not stored in the sink memory cluster, then such data is accessed from another memory cluster through remote access, but no migration is instructed. In another example, the data stored in the sink memory cluster is arranged to be classified into two parts. A first part of the data stored is to be searched or fetched only by processing threads originating in the sink memory cluster. A second part of the data is to be searched or fetched by processing threads migrating to the sink memory cluster from other memory clusters. As such, the first part of the data may have migration instructions embedded therein, while the second part of the data does not include any migration instructions. At block 1630, one or more processing threads executing in one or more of the plurality of memory clusters, are processed, for example, by corresponding processing engines, in accordance with at least one of the embedded migration instructions and the data stored in the sink memory cluster. For example, if the processing thread encounters migration instruction(s) then it is caused to migrate to another memory cluster according to the encountered instruction(s). Also if the processing thread migrates to the sink memory cluster, then the processing thread does migrate out of the sink memory cluster.

According to at least one aspect, migrating processing threads include at least one tree search thread or at least one bucket search thread. With regard to the instructions indicative of processing thread migrations, such instructions are embedded in a way that would cause migrated processing threads to migrate to a sink memory cluster or to a memory cluster in the path to a sink memory cluster. A path to a sink memory cluster is a sequence of memory clusters representing a migration flow path and ending with the sink memory cluster. The embedded instructions are also embedded in a way to prevent migration of a processing thread to a memory cluster from which the processing thread migrated previously. The instructions may further be designed to prevent a migrating processing thread arriving to a first memory cluster to migrate to a second memory cluster from which other migration threads migrate to the first memory cluster.

A person skilled in the art should appreciate that the RCDS 410, shown in FIG. 4, may be arranged according to another example of nested data structures. As such the processing engines 510 are defined in accordance with respective fetched data structures. For example, if the nested data structures include a table, a processing engine may defined as, for example, table fetching engine or table walk engine. Processing engines 510, according to at least one example, refer to separate hardware processors such as single-core processors or specialized processors included in the XBC 530. Alternatively, processing engines 510 may be functions performed by one or more hardware processors included in the XBC 530.

Embodiments may be implemented in hardware, firmware, software, or any combination thereof. It should be understood that the block diagrams may include more or fewer elements, be arranged differently, or be represented differently. It should be understood that implementation may dictate the block and flow diagrams and the number of block and flow diagrams illustrating the execution of embodiments of the invention.

While this invention has been particularly shown and described with references to example embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the invention encompassed by the appended claims. 

What is claimed is:
 1. A method of managing processing thread migrations within a plurality of memory clusters, the method comprising: embedding, in memory components of the plurality of memory clusters, instructions indicative of processing thread migrations, wherein the instructions indicative of processing thread migrations include instructions preventing migrating a processing thread to a memory cluster from which the processing thread migrated previously; and processing one or more processing threads, in one or more of the plurality of memory clusters, in accordance with at least one of the embedded migration instructions.
 2. A method according to claim 1, further comprising: storing, in one or more memory components of a particular memory cluster among the plurality of memory clusters, data configured to designate the particular memory cluster as a sink memory cluster, the sink memory cluster preventing an incoming migrated processing thread from migrating out of the sink memory cluster.
 3. A method according to claim 1, wherein in each of the plurality of memory clusters at least one processing engine is reserved to handle migrating processing threads.
 4. A method comprising: storing, in one or more memory components of a particular memory cluster among a plurality of memory clusters, data configured to designate the particular memory cluster as a sink memory cluster, the sink memory cluster preventing an incoming processing thread from migrating out of the sink memory cluster; and processing one or more processing threads, in one or more of the plurality of memory clusters, in accordance with one or more instructions indicative of processing thread migrations and the data stored in the one or more memory components of the sink memory cluster.
 5. A method according to claim 4, wherein the instructions indicative of processing thread migrations include instructions to cause migrated processing threads to be migrated out to a sink memory cluster or a memory cluster in a path to a sink memory cluster, a path to a sink memory cluster is a sequence of memory clusters representing a migration flow path and ending with the sink memory cluster.
 6. A method according to claim 4, wherein in each of the plurality of memory clusters at least one processing engine is reserved to handle migrating processing threads.
 7. A method according to claim 4, wherein the instructions indicative of processing thread migrations include instructions preventing migrating a processing thread to a memory cluster from which the processing thread migrated previously.
 8. A method according to claim 4, wherein storing the data in the sink memory cluster includes arranging at least a portion of the data into two parts, a first part of the data stored searched or fetched only by processing threads originating in the sink memory cluster and a second part of the data stored searched or fetched by processing threads migrating to the sink memory cluster from other memory clusters.
 9. A method according to claim 8, wherein the first part of the data includes at least one of the one or more instructions and the second part of the data does not include any migration instructions.
 10. An apparatus of managing processing thread migrations within a plurality of memory clusters, the apparatus comprising: one or more processors configured to: cause embedding, in memory components of the plurality of memory clusters, of instructions indicative of processing thread migrations, wherein the instructions indicative of processing thread migrations include instructions preventing migrating a processing thread to a memory cluster from which the processing thread migrated previously; process one or more processing threads, in one or more of the plurality of memory clusters, in accordance with at least one of the embedded migration instructions and the data stored in the one or more memory components of the sink memory cluster.
 11. An apparatus according to claim 10, wherein the one or more processors are further configured to: store, in one or more memory components of a particular memory cluster among the plurality of memory clusters, data configured to designate the particular memory cluster as a sink memory cluster, the sink memory cluster preventing an incoming migrated processing thread from migrating out of the sink memory cluster.
 12. An apparatus according to claim 10, wherein in each of the plurality of memory clusters at least one processing engine is reserved to handle migrating processing threads.
 13. An apparatus comprising: one or more processors configured to: store, in one or more memory components of a particular memory cluster among a plurality of memory clusters, of data configured to designate the particular memory cluster as a sink memory cluster, the sink memory cluster preventing an incoming processing thread from migrating out of the sink cluster; and process one or more processing threads, in one or more of the plurality of memory clusters, in accordance with one or more instructions indicative of processing thread migrations and the data stored in the one or more memory components of the sink memory cluster.
 14. An apparatus according to claim 13, wherein the instructions indicative of processing thread migrations include instructions to cause migrated processing threads to be migrated out to a sink memory cluster or a memory cluster in a path to a sink memory cluster, the path to a sink memory cluster being a sequence of memory clusters representing a migration flow path and ending with the sink memory cluster.
 15. An apparatus according to claim 13, wherein in each of the plurality of memory clusters at least one processing engine is reserved to handle migrating processing threads.
 16. An apparatus according to claim 13, wherein the instructions indicative of processing thread migrations include instructions preventing migrating a processing thread to a memory cluster from which the processing thread migrated previously.
 17. An apparatus according to claim 13, wherein storing the data in the sink memory cluster includes arranging at least a portion of the data into two parts, a first part of the data stored searched or fetched only by processing threads originating in the sink memory cluster and a second part of the data stored searched or fetched by processing threads migrating to the sink memory cluster from other memory clusters.
 18. An apparatus according to claim 17, wherein the first part of the data includes at least one of the one or more instructions and the second part of the data does not include any migration instructions. 